Pull Request

Description

Performed formal reviews for all 9 review-sets defined in .reviewmark.yaml and fixed the identified issues.

Review Sets Processed

Code Fixes

• RenameId.cs: Corrected wrong error message — 'spdx' → 'old' for the missing old input parameter
• RenameId.cs: Removed unreachable dead code (redundant oldId == newId check after an early return that already handles this case)
• Validate.cs: Corrected wrong command name in error message — 'to-markdown' → 'validate'
• Context.cs: Replaced int.Parse with int.TryParse so invalid --depth values throw InvalidOperationException (handled by Program.Main) instead of an unhandled FormatException
• Context.cs: Wrapped StreamWriter constructor in separate catch blocks for UnauthorizedAccessException, ArgumentException, NotSupportedException, and IOException, each producing a distinct descriptive InvalidOperationException message
• Runner.cs, DotnetRunner.cs, Query.cs: Fixed potential stdout/stderr deadlock — read both streams concurrently via ReadToEndAsync + Task.WaitAll instead of sequentially with ReadToEnd
• Runner.cs, DotnetRunner.cs: Added using var process to ensure the Process instance and its redirected streams are properly disposed after each test run

Documentation Fixes

• introduction.md: Fixed software structure diagram — moved RelationshipDirection.cs and SpdxHelpers.cs from the Utility (Subsystem) section to a correct Spdx (Unit Group) section
• spdxtool-system.md + commands/commands.md: Corrected class name CommandRegistry → CommandsRegistry throughout (to match the actual implementation)
• spdxtool-targets-system.md: Corrected MSBuild property name SpdxToolWorkflow → SpdxWorkflowFile (to match the actual targets file)
• utility.md: Corrected RelationshipDirection enum values — Forward/Reverse/Both → Parent/Child/Sibling (to match the actual implementation)

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Code quality improvement

Related Issues

Pre-Submission Checklist

Before submitting this pull request, ensure you have completed the following:

Build and Test

• Code builds successfully: dotnet build --configuration Release
• All unit tests pass: dotnet test --configuration Release
• Self-validation tests pass:
  dotnet run --project src/DemaConsulting.SpdxTool --configuration Release --framework net10.0
--no-build -- --validate
• Code produces zero warnings

Code Quality

• Code formatting is correct: dotnet format --verify-no-changes
• New code has appropriate XML documentation comments
• Static analyzer warnings have been addressed

Quality Checks

Please run the following checks before submitting:

• All linters pass: ./lint.sh (Unix/macOS) or cmd /c lint.bat / ./lint.bat (Windows)

Testing

• Added unit tests for new functionality
• Updated existing tests if behavior changed
• All tests follow the AAA (Arrange, Act, Assert) pattern
• Test coverage is maintained or improved

Documentation

• Updated README.md (if applicable)
• Updated ARCHITECTURE.md (if applicable)
• Added code examples for new features (if applicable)
• Updated requirements.yaml (if applicable)

Additional Notes

The --depth and --log exception-handling fixes align Context.Create with the documented /// <exception cref="InvalidOperationException"> contract, so callers (including Program.Main) already handle these cases correctly without displaying raw stack traces to the user.

The deadlock fix in Runner.cs / DotnetRunner.cs / Query.cs is latent but real — it manifests only when child process stderr output fills its OS buffer while the parent is blocked draining stdout.

The using var process fix in Runner.cs and DotnetRunner.cs ensures OS handles and redirected stream resources are released promptly, preventing handle leaks across long test runs.